We previously used taskId as a way to link a task with it's result stored in localStorage.

However, taskId was essentially an index value and we could only ever add new tasks to the end of existing ones. This PR moves over to using the task.name as the unique key.

Pros:

• Can reorder tasks safely
• Can add new tasks in any position
• Easier to parse result values stored in local storage

Cons:

• Task name becomes API. If we change a task name then pinned results will no longer match
• We can get tasks with duplicate task names. Mitigation: I wrote some code to throw an error if a duplicate is found
• This is a change in format for stored pinned values. Existing pins won't be able to be imported. We are not on stable versions yet so I think this is fine

I think on balance using the task.name is the better path for now. We could look at doing something more sophisticated in the future if we need to